Power Control for Wireless Communications Associated with Preempted Resources

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A wireless device may have different capabilities for preemption. A base station may use a signaling format to indicate a transmission power command and a preemption indicator. A wireless device may receive the signaling format and may determine, based on the transmission power command and the preemption indicator, whether to stop a transmission or to reduce a transmission power.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/188,822, filed Mar. 1, 2021, which is a continuation of U.S.application Ser. No. 16/370,433, filed on Mar. 29, 2019 and now U.S.Pat. No. 10,939,382, which claims the benefit of U.S. ProvisionalApplication No. 62/650,874, filed on Mar. 30, 2018. The above-referencedapplications are hereby incorporated by reference in their entirety.

BACKGROUND

A base station may communicate with a wireless device via uplink anddownlink channels. Wireless communications may be associated withvarious services, such as for ultra reliable low latency communications(URLLC), enhanced mobile broadband (eMBB) communications, and/or othercommunications. Some wireless communications may be preempted over otherwireless communications or may be transmitted using power levelsdifferent from other wireless communications, for example, based onservice type(s) and/or other information. It is desired to improvewireless communications without adversely increasing signaling overheadand/or decreasing spectral efficiency.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for multiplexingwireless communications. A base station may communicate with a wirelessdevice via uplink and downlink channels. A base station and/or awireless device may have different capabilities for processingmultiplexed data, preemption indication, and/or other signaling.Different downlink control signaling formats may be used to indicate apreemption for stopping an uplink transmission or to indicate a powerreduction associated with a preemption, for example, based on differentdevice capabilities. Using different downlink control signaling formatsmay increase downlink signal overhead and/or power consumption. Anenhanced downlink control information format may be used to indicate apreemption for stopping an uplink transmission and/or to indicate apower reduction associated with a preemption. The downlink controlinformation format may comprise a power control field and a preemptionindicator field. The power control field may be associated with thepreemption indicator field. A wireless device may determine to stop anuplink transmission or to reduce power for an uplink transmission on oneor more preempted resources, for example, based on the power controlfield and the preemption indicator field. A wireless device maydetermine preempted resource(s) based on one or more locations of thepreemption indicator field. The wireless device may reduce an uplinkpower on the preempted resource(s) or may stop an uplink transmission onthe preempted resource(s).

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16 shows an example of preemption control signaling.

FIG. 17 shows an example of preemption control signaling.

FIG. 18A shows an example of a power control command transmission.

FIG. 18B shows an example of a power control command transmission.

FIG. 19 shows an example of an uplink transmission power adjustmentbased on a power control command.

FIG. 20 shows an example of signaling for multiplexing uplink data withdifferent transmission durations.

FIG. 21 shows an example of DCI signaling for multiplexing uplink datawith different transmission durations.

FIG. 22A shows an example of a power control for multiplexing uplinkdata with different transmission durations.

FIG. 22B shows an example of DCI signaling for multiplexing uplink datawith different transmission durations.

FIG. 23 shows an example of a power control for multiplexing uplink datawith different transmission durations.

FIG. 24A shows an example of a power control for multiplexing uplinkdata with different transmission durations.

FIG. 24B shows an example of DCI signaling for multiplexing uplink datawith different transmission durations.

FIG. 25 shows an example of DCI signaling for multiplexing uplink datawith different transmission durations.

FIG. 26 shows an example of a power control for multiplexing uplink datawith different transmission durations.

FIG. 27 shows an example of DCI signaling for multiplexing uplink datawith different transmission durations.

FIG. 28 shows an example of DCI signaling for multiplexing uplink datawith different transmission durations in multiple cells.

FIG. 29 shows an example method for a power control for multiplexinguplink data with different transmission durations.

FIG. 30 shows an example method for a power control for multiplexinguplink data with different transmission durations.

FIG. 31 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto multiplexing data transmissions for wireless communications.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

-   -   3GPP 3rd Generation Partnership Project    -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ARQ Automatic Repeat Request    -   AS Access Stratum    -   ASIC Application-Specific Integrated Circuit    -   BA Bandwidth Adaptation    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   BPSK Binary Phase Shift Keying    -   BWP Bandwidth Part    -   CA Carrier Aggregation    -   CC Component Carrier    -   CCCH Common Control CHannel    -   CDMA Code Division Multiple Access    -   CN Core Network    -   CP Cyclic Prefix    -   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex    -   C-RNTI Cell-Radio Network Temporary Identifier    -   CS Configured Scheduling    -   CSI Channel State Information    -   CSI-RS Channel State Information-Reference Signal    -   CQI Channel Quality Indicator    -   CSS Common Search Space    -   CU Central Unit    -   DC Dual Connectivity    -   DCCH Dedicated Control Channel    -   DCI Downlink Control Information    -   DL Downlink    -   DL-SCH Downlink Shared CHannel    -   DM-RS DeModulation Reference Signal    -   DRB Data Radio Bearer    -   DRX Discontinuous Reception    -   DTCH Dedicated Traffic Channel    -   DU Distributed Unit    -   EPC Evolved Packet Core    -   E-UTRA Evolved UMTS Terrestrial Radio Access    -   E-UTRAN Evolved-Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplex    -   FPGA Field Programmable Gate Arrays    -   F1-C F1-Control plane    -   F1-U F1-User plane    -   gNB next generation Node B    -   HARQ Hybrid Automatic Repeat reQuest    -   HDL Hardware Description Languages    -   IE Information Element    -   IP Internet Protocol    -   LCD Logical Channel Identifier    -   LTE Long Term Evolution    -   MAC Media Access Control    -   MCG Master Cell Group    -   MCS Modulation and Coding Scheme    -   MeNB Master evolved Node B    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MN Master Node    -   NACK Negative Acknowledgement    -   NAS Non-Access Stratum    -   NG CP Next Generation Control Plane    -   NGC Next Generation Core    -   NG-C NG-Control plane    -   ng-eNB next generation evolved Node B    -   NG-U NG-User plane    -   NR New Radio    -   NR MAC New Radio MAC    -   NR PDCP New Radio PDCP    -   NR PHY New Radio PHYsical    -   NR RLC New Radio RLC    -   NR RRC New Radio RRC    -   NSSAI Network Slice Selection Assistance Information    -   O&M Operation and Maintenance    -   OFDM Orthogonal Frequency Division Multiplexing    -   PBCH Physical Broadcast CHannel    -   PCC Primary Component Carrier    -   PCCH Paging Control CHannel    -   PCell Primary Cell    -   PCH Paging CHannel    -   PDCCH Physical Downlink Control CHannel    -   PDCP Packet Data Convergence Protocol    -   PDSCH Physical Downlink Shared CHannel    -   PDU Protocol Data Unit    -   PHICH Physical HARQ Indicator CHannel    -   PHY PHYsical    -   PLMN Public Land Mobile Network    -   PMI Precoding Matrix Indicator    -   PRACH Physical Random Access CHannel    -   PRB Physical Resource Block    -   PSCell Primary Secondary Cell    -   PSS Primary Synchronization Signal    -   pTAG primary Timing Advance Group    -   PT-RS Phase Tracking Reference Signal    -   PUCCH Physical Uplink Control CHannel    -   PUSCH Physical Uplink Shared CHannel    -   QAM Quadrature Amplitude Modulation    -   QFI Quality of Service Indicator    -   QoS Quality of Service    -   QPSK Quadrature Phase Shift Keying    -   RA Random Access    -   RACH Random Access CHannel    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RA-RNTI Random Access-Radio Network Temporary Identifier    -   RB Resource Blocks    -   RBG Resource Block Groups    -   RI Rank indicator    -   RLC Radio Link Control    -   RRC Radio Resource Control    -   RS Reference Signal    -   RSRP Reference Signal Received Power    -   SCC Secondary Component Carrier    -   SCell Secondary Cell    -   SCG Secondary Cell Group    -   SC-FDMA Single Carrier-Frequency Division Multiple Access    -   SDAP Service Data Adaptation Protocol    -   SDU Service Data Unit    -   SeNB Secondary evolved Node B    -   SFN System Frame Number    -   S-GW Serving GateWay    -   SI System Information    -   SIB System Information Block    -   SMF Session Management Function    -   SN Secondary Node    -   SpCell Special Cell    -   SRB Signaling Radio Bearer    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   sTAG secondary Timing Advance Group    -   TA Timing Advance    -   TAG Timing Advance Group    -   TAI Tracking Area Identifier    -   TAT Time Alignment Timer    -   TB Transport Block    -   TC-RNTI Temporary Cell-Radio Network Temporary Identifier    -   TDD Time Division Duplex    -   TDMA Time Division Multiple Access    -   TTI Transmission Time Interval    -   UCI Uplink Control Information    -   UE User Equipment    -   UL Uplink    -   UL-SCH Uplink Shared CHannel    -   UPF User Plane Function    -   UPGW User Plane Gateway    -   VHDL VHSIC Hardware Description Language    -   Xn-C Xn-Control plane    -   Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme, for example, depending on transmission requirements and/or radioconditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Media Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCD for a logicalchannel and/or MAC CE may be configured for the wireless device by thebase station. The MAC sub-header corresponding to a MAC CE and/or a MACSDU may comprise an LCD associated with the MAC CE and/or the MAC SDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MA CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs indicating one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterInformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signaling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6 , FIG. 7A, FIG. 7B,FIG. 8 , and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel. A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for acarrier. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6 , asubframe may be divided into two equally sized slots 603 with 0.5 msduration. For example, 10 subframes may be available for downlinktransmission and 10 subframes may be available for uplink transmissionsin a 10 ms interval. Other subframe durations such as, for example, 0.5ms, 1 ms, 2 ms, and 5 ms may be supported. Uplink and downlinktransmissions may be separated in the frequency domain. Slot(s) mayinclude a plurality of OFDM symbols 604. The number of OFDM symbols 604in a slot 605 may depend on the cyclic prefix length. A slot may be 14OFDM symbols for the same subcarrier spacing of up to 480 kHz withnormal CP. A slot may be 12 OFDM symbols for the same subcarrier spacingof 60 kHz with extended CP. A slot may comprise downlink, uplink, and/ora downlink part and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a preemption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a wireless device is configured with a secondary carrier on a primarycell, the wireless device may be configured with an initial BWP forrandom access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base statin may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided a default DL BWP, a default BWP may be an initialactive DL BWP.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery procedure and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery procedure, and/or a contentionresolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery procedure associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery procedure, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery procedure. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For a beamfailure recovery procedure, the base station may configure the wirelessdevice with a different time window (e.g., bfr-ResponseWindow) tomonitor response to on a beam failure recovery request. The wirelessdevice may start a time window (e.g., ra-ResponseWindow orbfr-ResponseWindow) at a start of a first PDCCH occasion, for example,after a fixed duration of one or more symbols from an end of a preambletransmission. If the wireless device sends (e.g., transmits) multiplepreambles, the wireless device may start a time window at a start of afirst PDCCH occasion after a fixed duration of one or more symbols froman end of a first preamble transmission. The wireless device may monitora PDCCH of a cell for at least one random access response identified bya RA-RNTI, or for at least one response to a beam failure recoveryrequest identified by a C-RNTI, at a time that a timer for a time windowis running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC_Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC_Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC_Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station.

Wireless communications may be associated with various services, such asfor ultra reliable low latency communications (URLLC), enhanced mobilebroadband (eMBB) communications, and/or other communications. Somewireless communications (e.g., eMBB) may be preempted over otherwireless communications (e.g., URLLC), for example, based on servicetype(s), latency requirements, message size, device capability, deviceprocessing time, and/or any other information. Preemption may compriseuplink preemption and/or downlink preemption. A first message maypreempt a second message by using radio resources (e.g., time and/orfrequency resources) previously assigned to the second message (e.g.,via a downlink grant for a downlink radio resource, or via an uplinkgrant for an uplink radio resource). In some systems, a base station mayinitiate a preemption, for example, by sending (e.g., transmitting)group common downlink control information (DCI) (e.g., for stopping anuplink transmission) and/or a power control group common DCI (e.g., forreducing power for an uplink transmission). Such a base station may send(e.g., transmit), for example, a group common DCI using a first format(e.g., using DCI format 2_1) indicating uplink preemption for stoppingan uplink transmission and/or the base station may send (e.g., transmit)a power group common DCI using a second format (e.g., using DCI format2_2) for reducing a power of an uplink transmission. By sending (e.g.,transmitting) different DCI formats, downlink signal overhead of such abase station may increase. A wireless device in communication with sucha base station may increase power consumption by the wireless device,for example, by performing DCI blind decoding of such different DCIformats.

Wireless communications may be improved by using a single DCI format toindicate stopping transmission and/or a particular power level (e.g.,reduced power level). A base station may send (e.g., transmit), to awireless device that may receive, a first DCI to indicate stoppingtransmission and a second DCI to indicate a power reduction, wherein thefirst DCI and the second DCI may have the same format. A base stationmay use the single DCI format, for example, to indicate whether one ormore resources are preempted (e.g., an uplink preemption of an uplinkresource, and/or a downlink preemption of a downlink resource). The basestation may use the single DCI format, for example, to indicate a powerlevel for a group of wireless devices (e.g., a reduced power level for agroup of wireless devices communicating eMBB messages). The single DCIformat may comprise, for example, a preemption indicator field and apower control field. A wireless device may stop an uplink transmission,for example, based on or in response to receiving DCI comprising anuplink preemption indicator indicating one or more uplink radioresources are preempted. A wireless device may adjust its transmissionpower by a value indicated by the power control field (e.g., a powercontrol command of the power control field). The power control field maycomprise a predefined value, for example, to indicate a transmissionpower for one or more transmissions. The single DCI format may comprisea first value in the preemption indicator field and a second value inthe power control field. The wireless device may stop transmissionand/or adjust its transmission power for a transmission, for example,based on or in response to the preemption indicator field in the DCIand/or the power control field in the DCI.

A base station may reduce downlink signaling overhead and/or increasedownlink transmission throughput, for example, by sending (e.g.,transmitting) a single DCI indicating a power reduction and/or apreemption. A base station may be able to send (e.g., transmit) a singleDCI in place of at least two DCIs (e.g., a first DCI for preemption andat least a second DCI for power control). A wireless device may be ableto reduce power consumption by receiving, from the base station, DCI forpreemption and power control having a single DCI format. For example, bymonitoring for a single DCI format for preemption and power control, thewireless device may avoid monitoring a physical downlink control channel(PDCCH) for a plurality of DCI formats and/or the wireless device mayreduce DCI blind decoding of different DCI formats, which may result inreduced power consumption.

A base station (e.g., a gNB) may communicate with a wireless device viaa wireless network using one or more new radio technologies. The one ormore radio technologies may comprise at least one of multipletechnologies related to a physical layer, multiple technologies relatedto a medium access control layer, and/or multiple technologies relatedto a radio resource control layer. Enhancing the one or more radiotechnologies may improve performance of a wireless network, increase thesystem throughput, increase data rate of transmission, reduce batteryconsumption of a wireless device, improve latency of data transmissionbetween a base station and a wireless device, improve network coverageof a wireless network, and/or improve transmission efficiency of awireless network.

A base station may send (e.g., transmit) to and/or receive from awireless device one or more data packets via one or more radioresources. The one or more data packets may be one or more URLLC datapackets. The one or more data packets (e.g., URLLC packets) may be of asmall packet size (e.g., <100 bytes, <1 kB, etc.), which may requireultra-reliable (e.g., a block error rate less than 0.00001, less than0.000001, etc.) and low latency delivery between the base station andthe wireless device. The one or more data packets may be one or moreeMBB data packets. The one or more data packets (e.g., eMBB packets) maybe of a large packet size (e.g., >1000 bytes, >10 kB, etc.), which mayrequire large bandwidth and/or a large amount of radio resources.Multiplexing packets of a variety of types and/or for a variety ofservices, such as URLLC packets and eMBB packets, in a wireless systemmay improve the efficiency of radio resource utilization.

A base station may send (e.g., transmit) DCI via a PDCCH for at leastone of: a scheduling assignment, a scheduling grant, a slot formatnotification, a preemption indication, and/or a power-control command.The DCI may comprise at least one of: an identifier of a DCI format, adownlink scheduling assignment, an uplink scheduling grant, a slotformat indicator, a preemption indication, a power-control for PUCCHand/or PUSCH, and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format, a PDSCH resourceindication, a transport format, HARQ information, control information(e.g., which may be related to multiple antenna schemes), and/or acommand for a power control of the PUCCH.

An uplink scheduling grant DCI may comprise parameters indicating atleast one of: an identifier of a DCI format, a PUSCH resourceindication, a transport format, HARQ related information, and/or a powercontrol command of the PUSCH. Different types of control information maycorrespond to different DCI message sizes. Supporting multiple beamsand/or spatial multiplexing in the spatial domain, and noncontiguousallocation of resource blocks (RBs) in the frequency domain, may requirea larger scheduling message relative to an uplink grant allowing forfrequency-contiguous allocation. DCI may be categorized into differentDCI formats corresponding to a certain message size and/or usage.

A wireless device may monitor one or more PDCCHs for detecting one ormore DCI with one or more DCI formats. The wireless device may monitorone or more PDCCHs, for example, in a common search space or in awireless device-specific search space. A wireless device may monitorPDCCH with a limited set of DCI formats, for example, to save powerconsumption. A wireless device may consume power proportional to thenumber of DCI formats to be detected.

The information in the DCI formats for downlink scheduling may compriseat least one of: an identifier of a DCI format, a carrier indicator, anRB allocation, a time resource allocation, a bandwidth part indicator, aHARQ process number, one or more MCSs, one or more NDIs, one or moreRVs, MIMO related information, a downlink assignment index (DAI), a TPCfor PUCCH, an SRS request, and/or padding. MIMO related information maycomprise at least one of: a PMI, precoding information, a transportblock swap flag, a power offset between PDSCH and a reference signal, areference-signal scrambling sequence, a number of layers, one or moreantenna ports for the transmission, and/or a transmission configurationindication (TCI).

The information in the DCI formats used for uplink scheduling maycomprise at least one of: an identifier of a DCI format, a carrierindicator, a bandwidth part indication, a resource allocation type, anRB allocation, a time resource allocation, an MCS, an NDI, a phaserotation of the uplink DMRS, precoding information, a CSI request, anSRS request, an uplink index/DAI, a TPC for PUSCH, and/or padding.

A base station may perform CRC scrambling for DCI, for example, beforesending (e.g., transmitting) the DCI via a PDCCH. The base station mayperform CRC scrambling, for example, by adding multiple bits of at leastone wireless device identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI,TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI C-RNTI, SRS-TPC-RNTI, INT-RNTI,SFI-RNTI, etc.) on the CRC bits of the DCI. The addition may be binaryaddition. The wireless device may check the CRC bits of the DCI, forexample, if detecting the DCI. The wireless device may receive the DCI,for example, if the CRC is scrambled by a sequence of bits that is thesame as the at least one wireless device identifier.

A base station may send (e.g., transmit) one or more PDCCH in differentcontrol resource sets (coresets), for example to support a widebandwidth operation. A base station may send (e.g., transmit) one ormore RRC message comprising configuration parameters of one or morecoresets. A coreset may comprise at least one of: a first OFDM symbol, anumber of consecutive OFDM symbols, a set of resource blocks, and/or acontrol channel element (CCE)-to-resource element group (REG) mapping. Abase station may send (e.g., transmit) a PDCCH in a dedicated coresetfor particular purpose, such as beam failure recovery confirmation.

A wireless device may monitor PDCCH for detecting DCI in one or moreconfigured coresets, for example, to reduce the power consumption. Abase station may send, to a group of wireless devices, commoninformation, for example, by transmitting DCI with a dedicated DCIformat via a PDCCH. The common information may comprise at least one of:a slot format indication, one or more downlink preemption indications,one or more group power control commands for PUCCH/PUSCH of a group ofwireless devices, and/or one or more group power control commands forSRS transmission of one or more wireless devices.

A base station may send (e.g., transmit), to a wireless device, at leastone message comprising parameters indicating a group common identifier(e.g., RNTI). The group common RNTI may be the same for each wirelessdevice in a group of wireless devices. A wireless device may monitor aPDCCH for detecting DCI with a CRC scrambled by the group common RNTI,for example, if the wireless device is configured with the group commonRNTI. A wireless device may detect the DCI if a bit string, scrambled onthe CRC bits of the DCI, is the same as at least a part of a bit stringof the group common RNTI.

A base station may send (e.g., transmit) first DCI with a first DCIformat (e.g., DCI format 2_0) to each wireless device of a group ofwireless devices to indicate one or more slot formats. CRC bits of thefirst DCI may be scrambled by a first group common RNTI (e.g.,SFI-RNTI). The one or more slot formats may be identified by at leastone of: a number of downlink symbols, a number of uplink symbols, and/ora number of flexible symbols. A wireless device may monitor a PDCCH, fordetecting the first DCI, on one or more control resource sets and/or oneor more search spaces, for example, if the wireless device is configuredwith the first group common RNTI. The wireless device may determine aslot format for a slot based on the first DCI, for example, based ondetecting the first DCI. The wireless device may send (e.g., transmit)one or more uplink signals via uplink symbols. The wireless device mayreceive one or more downlink signals via downlink symbols. The sendingof uplink signals and/or the receiving of downlink signals may beaccording to the one or more slot formats indicated in the first DCI.

A first data packet (e.g., a URLLC packet) of a first wireless devicemay be multiplexed with a second data packet (e.g., an eMBB packet) of asecond wireless device on a PDSCH resource. The first data packet may besent (e.g., transmitted) with a first format (e.g., a first numerologyand/or a first scheduling granularity) on a first PDSCH resource. Thesecond data packet may be sent (e.g., transmitted) with a second format(e.g., a second numerology and/or a second scheduling granularity) on asecond PDSCH resource. The first PDSCH resource may be a part of thesecond PDSCH resource. The second PDSCH resource may be allocated forthe second wireless device by a downlink assignment indicated via aPDCCH. The first data packet (e.g., the URLLC data packet) for the firstwireless device may be sent (e.g., transmitted) via the first PDSCHresource that is a part of the second PDSCH resource, for example, ifthe first data packet (e.g., the URLLC packet) is required to be sentwith low latency. The second wireless device may receive, via the secondPDSCH resource, data that may comprise signals (e.g., on the part of thesecond PDSCH resource) for the first wireless device. The secondwireless device may incorrectly detect the second data packet, forexample, if there is no mechanism to indicate if there is a URLLC datatransmission via the allocated PDSCH resource. A base station may send(e.g., transmit) DCI comprising fields indicating one or more downlinkpreemption indicators to a group of wireless devices (e.g., includingthe second wireless device), indicating whether one or moretime/frequency resources are preempted (e.g., reserved for the firstwireless device), for example, to multiplex first data (e.g., URLLC dataor other data associated with a first service) and second data (e.g.,eMBB data or other data associated with a second service) on a PDSCH.

A wireless device may determine that there may be no transmission on oneor more time/frequency resources for the wireless device, for example,if the wireless device detects the DCI and if the field(s), in the DCI,that indicate the one or more time/frequency resources are preempted(e.g., reserved for other wireless devices). The wireless device maypuncture a received signal on the one or more time/frequency resources,for example, if the wireless device attempts to decode a downlink packetsent (e.g., transmitted) on a PDSCH resource at least partiallyoverlapped with the one or more time/frequency resources.

The wireless device may determine that there may be one or moretransmissions on the one or more time/frequency resources for thewireless device, for example, if the wireless device detects the DCI andif the field(s) in the DCI indicate the one or more time/frequencyresources are not preempted (e.g., not reserved for other wirelessdevices). The wireless device may decode a downlink packet sent (e.g.,transmitted) on a PDSCH resource at least partially overlapped with theone or more time/frequency resources, for example, if the PDSCH resourceis not allocated to other wireless devices.

A base station may send (e.g., transmit) DCI comprising fieldsindicating one or more downlink preemption indicators to a group ofwireless devices. The base station may send (e.g., transmit) the DCIwith a dedicated DCI format (e.g., DCI format 2_1). The DCI may be CRCscrambled by a second group common RNTI, for example, INT-RNTI. The basestation may send (e.g., transmit) at least one message comprisingparameters indicating the second group common RNTI to a wireless deviceand/or to multiple wireless devices. The at least one message maycomprise an RRC message, for example, an RRC connection reconfigurationmessage, an RRC connection reestablishment message, and/or an RRCconnection setup message. The wireless device may monitor a PDCCH on asearch space and/or on a control resource set for detecting the DCI, forexample, if the wireless device is configured with the second groupcommon RNTI.

FIG. 16 shows an example of preemption control signaling. The preemptioncontrol signaling may be applicable for a downlink preemption control oran uplink preemption control. A base station may multiplex first data(e.g., URLLC data) and second data (e.g., eMBB data) on a PDSCH. Thebase station may send (e.g., transmit) first DCI 1600, via a first PDCCHfor a first wireless device, indicating a first downlink assignment in aslot. The base station may send (e.g., transmit) second DCI 1602, via asecond PDCCH for a second wireless device, indicating a second downlinkassignment in the slot. The base station may send (e.g., transmit), toat least one wireless device, at least one message comprising parametersindicating a first RNTI value (e.g., INT-RNTI) for detecting third DCI1604 comprising a preemption indication (e.g., a downlink preemptionindication and/or an uplink preemption indication). The first RNTI maybe the same for each of the at least one wireless device. The at leastone message may further comprise a first control resource set, and/or afirst search space (e.g., a common search space or a wireless devicespecific search space) for detecting the third DCI 1604 comprising thepreemption indication.

The base station may send (e.g., transmit), via a third PDCCH on thefirst control resource set and/or the first search space, the third DCI1604 to the at least one wireless device (e.g., the first wirelessdevice and/or the second wireless device). The third DCI 1604 may be ofa DCI format (e.g., DCI format 2_1) and of a CRC scrambled by the firstRNTI. The third DCI 1604 may comprise fields indicating whether one ormore downlink radio resources are preempted. The one or more downlinkradio resources may be indicated in the at least one message. The basestation may send (e.g., transmit) the third DCI 1604 at the end of theslot or at the beginning of the next slot. Resources 1620 and resources1622 may be indicated as preempted. The third DCI 1604 may be used forindicating uplink preemption. The third DCI 1604 may be sent (e.g.,transmitted) before or during an eMBB uplink transmission, for example,if indicating uplink preemption on a PUSCH. The wireless device may stopand/or pause the eMBB transmission in a preempted PUSCH, for example,based on the third DCI 1604.

The first wireless device may detect the third DCI 1604 received via thefirst control resource set and/or the first search space, for example,if the wireless device is configured with the first RNTI. The firstwireless device may buffer the received data on the PDSCH 1610. Thefirst wireless device may buffer the received data on the PDSCH 1610before decoding, for example, if the third DCI 1604 is configured to besent (e.g., transmitted) at the end of the slot. The first wirelessdevice may puncture the received data on resource 1620, for example, ifthe first wireless device determines that the resource 1620 is preempted(e.g., which may be indicated by the third DCI 1604). The first wirelessdevice may decode the downlink data by using the buffered data after thepuncturing, for example, if the first wireless device determines thatthe resource 1620 is preempted (e.g., which may be indicated by thethird DCI 1604). The second wireless device may detect the third DCI1604 received via the first control resource set and/or the first searchspace, for example, if the second wireless device is configured with thefirst RNTI. The second wireless device may buffer the received data onthe PDSCH 1612. The second wireless device may buffer the received dataon the PDSCH 1612 before decoding, for example, if the third DCI 1604 isconfigured to be sent (e.g., transmitted) at the end of the slot. Thesecond wireless device may puncture the received data via the resource1612, for example, if the second wireless device determines thatresource 1622 is preempted (e.g., which may be indicated by the thirdDCI 1604). The second wireless device may decode the downlink data byusing the buffered data after the puncturing, for example, if the secondwireless device determines that resource 1622 is preempted (e.g., whichmay be indicated by the third DCI 1604).

The third DCI 1604 may comprise one or more fields indicating whetherone or more radio resources are preempted. The one or more radioresources may be indicated in the at least one message. The third DCI1604 may comprise one preemption indicator and/or a DCI formatindicator, for example, if a wireless device (e.g., the first wirelessdevice, the second wireless device, etc.) is configured with one cell.The DCI format indicator may indicate the third DCI 1604 is used to send(e.g., transmit) the one preemption indicator, if the DCI formatindicator is set to a first value. One or more bits of the preemptionindicator may correspond to one of the one or more radio resources. Thecorrespondence between a bit in the preemption indicator and a radioresource may be indicated by the at least one message. A radio resourceassociated with a bit of the preemption indicator may be preempted, forexample, if the bit of the preemption indicator is set to a first value,such as one. A radio resource associated with a bit of the preemptionindicator may not be preempted, for example, if the bit of thepreemption indicator is set to a second value, such as zero.

The third DCI 1604 may comprise multiple preemption indicators and/or aDCI format indicator, for example, if a wireless device (e.g., the firstwireless device, the second wireless device, etc.) is configured withmultiple cells. The DCI format indicator may indicate the third DCI 1604may be used to send (e.g., transmit) the multiple preemption indicators,for example, if the DCI format indicator is set to a first value. One ormore of the multiple preemption indicators may correspond to one of themultiple cells. The correspondence between a preemption indicator and acell may be indicated by the at least one message. One or more bits of apreemption indicator may correspond to one of multiple radio resourcesof a cell corresponding to the preemption indicator, for example, if thecell is associated with the preemption indicator. The correspondence maybe indicated by the at least one message. A radio resource associatedwith a bit of a preemption indicator, on a cell associated with thepreemption indicator, may be preempted, for example, if the bit of thepreemption indicator is set to a first value, such as one. A radioresource associated with a bit of a preemption indicator, on a cellassociated with the preemption indicator, may not be preempted, forexample, if the bit of the preemption indicator is set to a secondvalue, such as zero.

A base station may send (e.g., transmit) fourth DCI for a third wirelessdevice (e.g., a URLLC wireless device, a vehicle-to-everything (V2X)wireless device, an Internet-of-Things (IoT) wireless device, etc.)indicating a downlink assignment for a transmission comprising URLLCdata, V2X data, IoT data, or any other type of data. The downlinkassignment may be overlapped with PDSCH 1610 and/or PDSCH 1612. The basestation may send (e.g., transmit) URLLC data, for the third wirelessdevice via the resource 1620 and/or the resource 1622, that may beindicated as preempted by the third DCI 1604. The third wireless devicemay receive the URLLC data on the slot, for example, after receiving thefourth DCI. This procedure may reduce the transmission latency by notwaiting for the next slot. The first wireless device may receive thedata transmitted on PDSCH 1610, for example, after receiving the thirdDCI 1604. The first wireless device may identify that the resource 1620is not for the first wireless device. The first wireless device maydetermine that the corresponding data received on the resource 1620 maybe punctured. The second wireless device may receive the datatransmitted on PDSCH 1622. The second wireless device may identify thatthe resource 1622 is not for the second wireless device. The secondwireless device may determine that the corresponding data received onthe resource 1622 may be punctured.

FIG. 17 shows an example of preemption control signaling. The preemptioncontrol signaling may be applicable for a downlink preemption control oran uplink preemption control. A base station 1710 may multiplex downlinktransmissions with different transmission durations and/or reliabilityrequirements. A wireless device 1721 and a wireless device 1722 may beconfigured with a first group RNTI. The wireless device 1721 or thewireless device 1722 may send (e.g., transmit) or receive one or moredata packets for a first transmission duration (e.g., 1 slot, atransmission duration of the PDSCH 1610, a transmission duration of thePDSCH 1612, etc.). The wireless device 1733 may be capable of sending(e.g., transmitting) or receiving one or more data packets for a secondtransmission duration (e.g., less than 1 slot, such as 1, 2, or severalsymbols, a transmission duration in the resources 1620 and 1622, etc.).The wireless device 1721 may send or receive first data (e.g., thewireless device 1721 may receive a first DL packet via a first DLassignment or send a first UL packet via a first UL grant). The wirelessdevice 1722 may send or receive second data (e.g., the wireless device1722 may receive a second DL packet via a second DL assignment or send asecond UL packet via a second UL grant). The base station may send(e.g., transmit) first DCI 1741 addressed to the first group RNTIindicating whether one or more radio resources (e.g., DL radio resourcesor UL radio resources) are preempted (or reserved for other wirelessdevices, such as the wireless device 1733) or not preempted. The firstDCI 1741 may be scrambled with the first group RNTI. The first DCI 1741may be similar to the third DCI 1604. The wireless device 1721 maypuncture the first data on a first one of the one or more radioresources, for example, if the first DCI 1741 indicates the first one ofthe one or more radio resources is preempted and if the first DLassignment or the first UL grant indicates a data transmission in thefirst one of the one or more radio resources. The wireless device 1721may decode the first data without puncturing, for example, if the firstDCI 1741 does not indicate the one or more radio resources arepreempted. The wireless device 1722 puncture the second data on a secondone of the one or more radio resources, for example, if the first DCI1741 indicates the second one of the one or more radio resources ispreempted and if the second DL assignment or the second UL grantindicates a data transmission in the second one of the one or more radioresources. The wireless device 1722 may decode the second data withoutpuncturing, for example, if the first DCI 1741 does not indicate the oneor more radio resources are preempted. The first one of the one or moreradio resources and the second one of the one or more radio resourcesmay comprise the same time resource(s). The base station 1710 may send(e.g., transmit) second DCI 1751 for the wireless device 1733 indicatinga third DL assignment associated with a third one of the one or moreradio resources (or indicating a third UL grant associated with thethird one of the one or more radio resources). The wireless device 1733may receive a downlink packet (or send an uplink packet) via the thirdone of the one or more radio resources, for example, based on detectingthe second DCI 1751. The third one of the one or more radio resourcesmay be overlapped with the first one of the one or more radio resourcesand with the second one of the one or more radio resources.

A base station may send (e.g., transmit), to a group of wireless device,a wireless device group common DCI indicating downlink preemptioninformation, for example, for multiplexing URLLC data and eMBB data in adownlink transmission. The wireless device group common DCI may have DCIformat 2_1 and may be CRC scrambled by a wireless device group RNTI(e.g., INT RNTI). The group common signaling using the wireless devicegroup common DCI may reduce downlink signaling overhead, instead ofsending different DCIs for each wireless device of the group of wirelessdevices for a preemption indication.

Data with different durations (e.g., URLLC data and eMBB data) may bemultiplexed in downlink for one or more wireless devices. A base stationmay send (e.g., transmit) a group common signal (e.g., DCI with DCIformat 2_1 and CRC scrambled by INT-RNTI) to a group of wireless devices(e.g., including a first wireless device), indicating whether one ormore radio resources in one or more slots are preempted, for example, ifthe base station multiplexes a first type of data (e.g., eMBB data) ofthe first wireless device with a second type of data (e.g., URLLC data)of a second wireless device. The base station may reliably send (e.g.,transmit) the URLLC data for the second wireless device via the one ormore radio resources, for example, based on the group common signaling.

A wireless device may have data (e.g., URLLC data) to be sent within ashort duration (e.g., a transmission duration shorter than atransmission duration for eMBB data) in an uplink slot. A transmissionof the URLLC data may be more urgent than a transmission of the eMBBdata. It may be preferable (e.g., necessary) to schedule an uplink radioresource for the transmission of the URLLC data in the uplink slot assoon as possible. There may be no available uplink radio resource in theuplink slot, for example, if uplink radio resources are fully allocatedto other wireless devices. The URLLC data may be scheduled with a higherpriority over other scheduled data (e.g., eMBB data). It may bebeneficial to stop and/or suspend an ongoing uplink transmission (e.g.,eMBB data or other scheduled data) on one or more uplink radioresources, for example, to schedule the URLLC data quickly. One or moregroup common signaling schemes may not support multiplexing of uplinktransmissions with different transmission durations or reliabilities(e.g., multiplexing URLLC data with eMBB data). Group common signalingmay be configured and provided to support multiplexing of uplinktransmissions with different durations and/or reliabilities.

A base station may be capable of receiving, from multiple wirelessdevices, multiplexed data packets on an uplink radio resource, forexample, by using an interference cancellation. The base station maydetect a first data packet transmitted from a first wireless device. Thebase station may detect one or more second data packet transmitted fromat least one second wireless device, for example, by cancellinginterference caused by the first data packet multiplexed with the one ormore second data packet. The capability of detecting the one or moresecond data packet based on one or more interference cancelationalgorithms may allow the base station to flexibly schedule uplink datawith different transmission duration, for example, if the interferenceis in a tolerable range.

A base station may send, to a plurality of wireless devices, powercontrol indications, for example, if the base station is capable ofreceiving, from the plurality of wireless devices, multiplexed datapackets sent (e.g., transmitted) on one or more uplink radio resources.The power control indications may be used to control (e.g., limit,reduce, etc.) interference on first data (e.g., URLLC data). A powercontrol signaling may be used, by the base station, to control theinterference within a tolerable range and to detect the first data, forexample, if multiplexing of data transmissions is performed withdifferent transmission durations. A base station may send (e.g.,transmit) a power control command in first DCI addressed to a wirelessdevice or a power control command in second DCI addressed to a group ofwireless devices.

FIG. 18A shows an example of a power control command transmission. Abase station 1810A may send (e.g., transmit) a transmission powercontrol (TPC) command comprised in DCI addressed to a wireless device(e.g., a wireless device 1820A in FIG. 18A). The DCI may comprise anuplink grant with a particular DCI format (e.g., DCI format 0_0 or 0_1).The wireless device 1820A may send (e.g., transmit) an uplink signalwith a transmission power determined based on the TPC command.

FIG. 18B shows an example of a power control command transmission. Abase station 1810B may send (e.g., transmit) one or more transmissionpower control (TPC) commands comprised in DCI addressed to a group ofwireless devices 1820B. The DCI may comprise indications of TPC commandsfor PUCCH and/or PUSCH transmission. The DCI may be sent (e.g.,transmitted) on a PDCCH with a first DCI format (e.g., DCI format 2_2).The DCI may be addressed to a group of wireless devices associated witha group RNTI (e.g., TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, etc.). The DCI maycomprise indications of TPC commands for SRSs, and the DCI may be sent(e.g., transmitted) on a PDCCH with a second DCI format (e.g., DCIformat 2_3). The DCI may be addressed to a group of wireless devicesassociated with a group RNTI (e.g., TPC-SRS-RNTI).

FIG. 19 shows an example of an uplink transmission power adjustmentbased on a power control command. A base station may send (e.g.,transmit) one or more TPC commands (e.g., N TPC commands) comprised inDCI 1930 addressed to one or more wireless devices. TPC command 1 in theDCI 1930 may be associated with a wireless device 1920-1. TPC command 2in the DCI 1930 may be associated with a wireless device 1920-2. TPCcommand N in the DCI 1930 may be associated with a wireless device1920-N. The association between a TPC command and a wireless device maybe configured by one or more messages (e.g., an RRC message).

The one or more wireless devices 1920-1, 1920-2, . . . , 1920-N maydetermine a transmission power according to the one or more TPC commandsin the DCI 1930. The wireless device 1920-1 may send (e.g., transmit) afirst uplink signal with a first transmission power based on the TPCcommand 1. The wireless device 1920-2 may send (e.g., transmit) a seconduplink signal with a second transmission power based on the TPC command2. The wireless device 1920-N may send (e.g., transmit) an Nth uplinksignal with an Nth transmission power based on the TPC command N. Thetime for applying a TPC command may depend on a system configuration(e.g., FDD or TDD). A wireless device may determine a transmission powerof an uplink transmission to be sent in slot 5, based on a TPC commandreceived in slot 1, for example, in an FDD system. A time gap between aTPC command reception and an uplink transmission may be differentlyconfigured, for example, in a TDD system.

A TPC command in DCI may be a bit string in a length (e.g., bitwidth) of1 or 2 bits. A TPC command with a first TPC value (e.g., “00”) mayindicate a first power adjustment value (e.g., −1 dB). A wireless devicemay reduce, based on the first power adjustment value (e.g., −1 dB), atransmission power of a next transmission from the current transmissionpower, for example, if the wireless device determines that the TPCcommand indicates the first TPC value (e.g., “00”). A wireless devicemay reduce a transmission power at most by 1 dB or increase atransmission power at most by 3 dB, according to a TPC command of one ormore power control configurations.

A base station may indicate a wireless device to stop (or suspend) anongoing uplink transmission or may indicate a wireless device to reduce,based on interference cancellation capability of the base station, atransmission power for the ongoing uplink transmission, for example, ifthe base station and/or the wireless device support multiplexing uplinktransmissions with different transmission durations. Some power controlprocedures (e.g., the power control procedure shown in FIG. 18A) may notbe efficient in terms of DCI overhead, because each involved wirelessdevice (e.g. in a group of wireless devices) in multiplexing may beindicated with individual DCI addressed to that wireless device. Somepower control procedures (e.g., the power control procedure shown inFIG. 18B) may not support an indication of stopping (or suspending) anongoing uplink transmission. Some power control procedures (e.g., boththe power control procedure shown in FIG. 18A and the power controlprocedure shown in FIG. 18B) may not support an indication of a powerreduction with more than 1 dB, for example, since the TPC command in thepower control procedures may at most indicate −1 dB. A greater powerreduction (e.g., reducing more than 1 dB) may be necessary to ensurethat interference on a first type of data (e.g., an URLLC data packet)is in a tolerable range. An efficient power control and/or interferencecontrol procedure for supporting multiplexing uplink transmission withdifferent transmission durations and/or reliabilities may be configured.

FIG. 20 shows an example of signaling for multiplexing uplink data withdifferent transmission durations. A base station may send (e.g.,transmit), to one or more wireless devices of a group of wirelessdevices (e.g., wireless devices 2021 and 2022), at least one firstmessage comprising parameters indicating at least one of: an RNTI valueand/or a DCI format. The RNTI value may be a value for a group RNTIwhich may be the same for the group of wireless devices. The DCI formatmay be DCI format 2_1, DCI format 2_2, DCI format 2_3, or other DCIformats.

The RNTI value may be different from a second RNTI (e.g., INT-RNTI), forexample, if the DCI format is DCI format 2_1. The RNTI value may bedifferent from a third RNTI (e.g., TPC-PUCCH-RNTI or TPC-PUSCH-RNTI),for example, if the DCI format is DCI format 2_2. The RNTI value may bedifferent from a fourth RNTI (e.g., TPC-SRS-RNTI), for example, if theDCI format is DCI format 2_3. A base station and/or a wireless devicemay correctly determine content and/or information in the DCI, forexample, by associating different RNTI values with different groupcommon signaling while using the same DCI format.

The wireless device 2021 may be identified by a first C-RNTI. Thewireless device 2022 may be identified by a second C-RNTI. A wirelessdevice 2023 may be identified by a third C-RNTI. The wireless device2021 may send (e.g., transmit) one or more uplink data within a firsttransmission duration 2040 (e.g., in one or more slots). The wirelessdevice 2022 may send (e.g., transmit) one or more uplink data 2022within the first transmission duration 2040 (e.g., in one or moreslots). The wireless device 2023 may send (e.g., transmit) one or moreuplink data 2033 within a second transmission duration 2043 (e.g., inless than one slot, such as 1, 2 or several symbols).

The at least one first message may further comprise at least one of: afirst control resource set, a first search space, a first monitoringperiodicity, and/or at least a set of multiple uplink radio resourcesfor the group of wireless devices. Each of multiple uplink radioresources may be identified by at least one of: a time resource, afrequency resource, a beam index, and/or an orthogonal code index. Thebase station may send (e.g., transmit) at least one second messagecomprising parameters indicating at least one of: a second controlresource set, a second search space, and/or a second monitoringperiodicity for the wireless device 2023.

The wireless device 2021 may send (e.g., transmit) first uplink data viaa first PUSCH resource 2031 allocated via a first uplink grant 2051. Thewireless device 2022 may send (e.g., transmit) second uplink data via asecond PUSCH resource 2032 allocated via a second uplink grant 2052.

The base station 2010 may send (e.g., transmit) first DCI 2060 addressedto the first RNTI (e.g., for the group of wireless devices comprisingthe wireless devices 2021 and 2022). The first DCI 2060 may be sent viathe first control resource set and/or the first search space of a PDCCHwith the first periodicity (e.g., in a first slot or in a first symbolduration). The first DCI 2060 with the DCI format may comprise at leastone of: a TPC command and/or one preemption indicator comprising anumber of bits (e.g., 7 or 14 bits).

FIG. 21 shows an example of DCI signaling for multiplexing uplink datawith different transmission durations. Group DCI 2160 (e.g., the firstDCI 2060) may comprise a TPC field 2161 and a preemption indicator field2162. The TPC field 2161 may comprise one or more values of one or moreTPC commands. The preemption indicator field 2162 may comprise one ormore values of one or more preemption indicators. Each bit of the one ormore preemption indicators may be associated with one of multiple uplinkradio resources 2171. The multiple uplink radio resources 2171 (e.g.,multiple uplink radio resources 2071 of FIG. 20 ) may comprise frequencyand time resources configured for multiplexing uplink data withdifferent transmission durations. The first bit of the one or morepreemption indicators may be associated with the first uplink radioresource of the multiple uplink radio resources 2171. The Nth bit 2162-Nof the one or more preemption indicators may be associated with the Nthuplink radio resource 2171-N of the multiple uplink radio resources2171.

Each TPC command may have a value represented by a number of bits (e.g.,1 or 2 bits). A TPC command may indicate a power reduction value basedon the value of the TPC command. A power reduction corresponding to afirst value (e.g., zero) of the TPC command may be a first dB value(e.g., 3 dB), for example, if the TPC command has a value of 1 bit. Apower reduction corresponding to a second value (e.g., one) of the TPCcommand may be a second dB value (e.g., 6 dB), for example, if the TPCcommand has a value of 1 bit. A power reduction corresponding to a firstvalue (e.g., “00”) of the TPC command may be a first dB value (e.g., 1dB), a power reduction corresponding to a second value (e.g., “01”) ofthe TPC command may be a second dB value (e.g., 3 dB), a power reductioncorresponding to a third value (e.g., “10”) of the TPC command may be athird dB value (e.g., 6 dB), and a power reduction corresponding to afourth value (e.g., “11”) of the TPC command may be a fourth dB value(e.g., 9 dB), for example, if the TPC command has a value of 2 bits.

The one or more preemption indicators in the group DCI 2160 may indicatewhether one or more resources of the multiple uplink radio resources2171 are preempted (e.g., reserved) or not. One of the multiple uplinkradio resources 2171 associated with a bit of the preemption indicatorfield 2162 may not be preempted, for example, if the bit of thepreemption indicator field 2162 is set to a first value (e.g., zero).One of the multiple uplink radio resources 2171 associated with a bit ofthe preemption indicator field 2162 may be preempted, for example, ifthe bit of the preemption indicator field 2162 is set to a second value(e.g., one). A wireless device (e.g., the wireless devices 2021 and2022) may determine that an uplink radio resource being preempted as anuplink radio resource being assigned for other wireless devices.

The wireless device 2021 of FIG. 20 may determine whether one or moreresources of the multiple uplink radio resources 2071 are preempted ornot, for example, based on a preemption indicator field comprised in thefirst DCI 2060. The wireless device 2022 may adjust a transmission powerfor a PUSCH transmission scheduled on one or more preempted resources ofthe second PUSCH resource 2032, for example, based on a TPC commandfield and the preemption indicator field of the first DCI 2060.

FIG. 22A shows an example of a power control for multiplexing uplinkdata with different transmission durations. FIG. 22B shows an example ofDCI signaling for multiplexing uplink data with different transmissiondurations. The first PUSCH resource 2031 may comprise at least one ofthe multiple uplink radio resources 2071. The at least one of themultiple uplink radio resources 2071 may be preempted, and thepreemption may be indicated by the first DCI 2060. The wireless device2021 may determine a power reduction, for example, based on a value ofthe TPC command field of the first DCI 2060. The wireless device 2021may determine an adjusted transmission power, for example, based on thepower reduction and a normal transmission power. The normal transmissionpower may be a transmission power for a transmission via a non-preemptedradio resource. The adjusted transmission power may be determined byreducing the normal transmission power by a value of the powerreduction. The normal transmission power may be a transmission powerwith which the wireless device 2021 transmits the first uplink databefore receiving the first DCI 2060. The wireless device 2021 maycontinue transmitting a subsequent portion of the first uplink data withthe adjusted transmission power (e.g., in a second slot or in a secondsymbol duration).

FIG. 23 shows an example of a power control for multiplexing uplink datawith different transmission durations. The base station 2010 (e.g., thebase station 2310) may send, to a plurality of wireless devices 2320-1,2320-2, . . . , and 2320-K (e.g., the wireless devices 2021 and 2022),the first DCI 2060 (e.g., group DCI 2360) within the first slot (e.g.,slot 1). The group DCI 2360 may comprise a TPC command field and a ULpreemption indicator field. The plurality of wireless devices 2320-1,2320-2, . . . , and 2320-K may send, to the base station 2310 and basedon the TPC command field of the group DCI 2360, PUSCHs within the secondslot (e.g., slot m). The transmission powers of the PUSCHs transmittedwithin the second slot may be adjusted based on a value of the TPCcommand field of the group DCI 2360. A duration of the second slot, orthe second symbol duration, for applying the adjusted transmission powermay be the same as a duration of the first slot, or a first symbolduration, for receiving the first DCI 2060. The second slot for applyingthe adjusted transmission power may begin a number of slots (e.g., 1, 2,3, or 4 slots) after the first slot for receiving the first DCI 2060(e.g., the DCI 2360). The second symbol duration for applying theadjusted transmission power may begin a number of symbols (e.g., 1, 2, .. . , or 13 symbols) after the first symbol duration for receiving thefirst DCI 2060.

The first PUSCH resource 2031 of FIG. 20 may comprise at least one ofthe multiple uplink radio resources 2071, which is not preempted (e.g.,indicated by the first DCI 2060). The wireless device 2021 may continueto perform the first uplink data transmission without adjusting thenormal transmission power (e.g., the TPC command for adjusting thenormal transmission power may not be used for non-preempted resources).

The wireless device 2022 may determine whether the multiple uplink radioresources 2071 are preempted or not, for example, based on thepreemption indicator field comprised in the first DCI 2060. The wirelessdevice 2022 may adjust a transmission power for a PUSCH transmissionscheduled on one or more preempted resources of the second PUSCHresource 2032, for example, based on the TPC command field and thepreemption indicator field of the first DCI 2060. The second PUSCHresource 2032 may comprise at least one of the multiple uplink radioresources 2071, which may be preempted (e.g., the preemption may beindicated by the first DCI 2060). The wireless device 2022 may determinea power reduction, for example, based on a TPC command of the first DCI2060. The wireless device 2022 may determine an adjusted transmissionpower for a next uplink transmission occasion in the multiple uplinkradio resources 2071, for example, based on the power reduction and anormal transmission power of the wireless device 2022. The normaltransmission power of the wireless device 2022 may be a transmissionpower, of the wireless device 2022, for an uplink transmission via anon-preempted radio resource. The wireless device 2022 may continuetransmitting the second uplink data with the adjusted transmission power(e.g., in the second slot or in the second symbol duration). A durationof the second slot, or the second symbol duration, for applying theadjusted transmission power may be the same as a duration of the firstslot, or the first symbol duration, for receiving the first DCI 2060.The second slot for applying the adjusted transmission power may begin anumber of slots (e.g., 1, 2, 3, or 4 slots) after the first slot forreceiving the first DCI 2060 (e.g., the DCI 2360). The second symbolduration for applying the adjusted transmission power may begin a numberof symbols (e.g., 1, 2, . . . , or 13 symbols) after the first symbolduration for receiving the first DCI 2060.

The second PUSCH resource 2032 may comprise at least one of the multipleuplink radio resources 2071, which may not be preempted (e.g., thepreemption may be indicated by the first DCI 2060). The wireless device2022 may continue the second uplink data transmission without adjustingthe normal transmission power (e.g., the TPC command for adjusting thenormal transmission power may not be used for non-preempted resources).

A base station may send (e.g., transmit) second DCI (e.g., DCI 2053)addressed to one or more wireless devices (e.g., the wireless device2023) associated with the third C-RNTI. The second DCI may indicate anuplink grant for the wireless device 2023. The uplink grant may compriseat least one of the multiple radio resources 2071. The wireless device2023 may send (e.g., transmit), via the preempted resource(s) 2033 andbased on the uplink grant, uplink data.

FIG. 24A shows an example of a power control for multiplexing uplinkdata with different transmission durations. FIG. 24B shows an example ofDCI signaling for multiplexing uplink data with different transmissiondurations. The TPC command of the first DCI 2060 may be set to apredefined value. The predefined value may indicate a suspending orstopping of an ongoing uplink transmission.

A first value (e.g., zero) of a TPC command field of the first DCI 2060may indicate a power reduction of a first value (e.g., a 3 dB powerreduction), for example, if the TPC command of the first DCI 2060 is a1-bit value. A second value (e.g., one) of the TPC command field of thefirst DCI 2060 may indicate that one or more wireless devices stop orsuspend an ongoing uplink transmission on at least one of the multipleuplink radio resources 2071, for example, based on the one or morepreemption indicators of the first DCI 2060. A TPC command of the firstDCI 2060 may have a 2-bit value or an m-bit value having more than 2bits. A third value (e.g., “00” or “11”) of a TPC command field of thefirst DCI 2060 may indicate that one or more wireless devices stop orsuspend an ongoing uplink transmission on at least one of the multipleuplink radio resources 2071, for example, based on the one or morepreemption indicators of the first DCI 2060.

The first PUSCH resource 2031 may comprise at least one of the multipleuplink radio resources 2071, which may be preempted by the first DCI2060. The wireless device 2021 may stop or suspend the first uplink datatransmission, for example, if the TPC command is set to the predefinedvalue. The wireless device 2021 may stop or suspend transmitting thefirst uplink data. The wireless device 2021 may stop the transmissionfrom the beginning of the second slot or the second symbol duration.

The first PUSCH resource 2031 may comprise at least one of the multipleuplink radio resources 2071, which is not preempted by the first DCI2060. The wireless device 2021 may continue the first uplink datatransmission without stopping or suspending the transmission (e.g., theTPC command for stopping or suspending the uplink transmission may notbe used for non-preempted resources).

The second PUSCH resource 2032 may comprise at least one of the multipleuplink radio resources 2071, which is preempted by the first DCI 2060.The wireless device 2022 may stop or suspend the second uplink datatransmission, for example, if the TPC command is set to the predefinedvalue. The wireless device 2022 may stop or suspend transmitting thesecond uplink data. The wireless device 2022 may stop the transmissionfrom the beginning of the second slot or the second symbol duration.

The second PUSCH resource 2032 may comprise at least one of the multipleuplink radio resources 2071, which is not preempted by the first DCI2060. The wireless device 2022 may continue the second uplink datatransmission without stopping or suspending the transmission (e.g., theTPC command for stopping or suspending the uplink transmission may notbe used for non-preempted resources).

A base station may indicate a power control value (e.g., a power valuefor reducing power or stopping or suspending a transmission for one ormore preempted resources) via higher layer signaling (e.g., an RRCmessage), for example, if the power control value to supportmultiplexing uplink data with different transmission durations is notdynamic (e.g., semi-static). The power reduction indication or the powerstopping indication may be provided by one or more RRC messages.

A base station may send (e.g., transmit) at least one first messagecomprising parameters indicating at least one of: a first RNTI value, aDCI format, and/or at least one power reduction indication for a groupof wireless devices (e.g., the wireless devices 2021 and 2022). The atleast one first message may further comprise at least one of: a firstcontrol resource set, a first search space, a first monitoringperiodicity, and/or at least a set of multiple uplink radio resources.Each of the multiple uplink radio resources may be identified by atleast one of: a time resource, a frequency resource, a beam index,and/or an orthogonal code index. An indication of the at least one powerreduction may be set to a predefined value indicating stopping (orsuspending) an ongoing uplink transmission. A value of at least onepower reduction may indicate a power reduction value (e.g., in dB).

The base station may send (e.g., transmit) first DCI addressed to one ormore wireless devices associated with a first RNTI. The first DCI may besent, for example, via the first control resource set and/or the firstsearch space of a PDCCH with the first monitoring periodicity in a firstslot or a first symbol. The first DCI with the DCI format may compriseat least a preemption indicator comprising a number of bits (e.g., 7 or14 bits). Each bit of the preemption indicator may be associated withone of the multiple uplink radio resources. The first bit of thepreemption indicator may be associated with the first uplink radioresource of the multiple uplink radio resources, the second bit of thepreemption indicator may be associated with the second uplink radioresource of the multiple uplink radio resources, and the Nth bit of thepreemption indicator may be associated with the Nth uplink radioresource of the multiple uplink radio resources.

The preemption indicator in the first DCI may indicate whether or notone or more resources of the multiple uplink radio resources arepreempted (e.g. or reserved). One of the multiple uplink radio resourcesassociated with a bit of the preemption indicator may not be preempted,for example, if the bit of the preemption indicator is set to a firstvalue (e.g., zero). One of the multiple uplink radio resourcesassociated with a bit of the preemption indicator may be preempted, forexample, if the bit of the preemption indicator is set to a second value(e.g., one). One or more wireless devices may determine an uplink radioresource being preempted as an uplink radio resource being assigned toother wireless devices.

One or more wireless devices may determine whether one or more resourcesof the multiple uplink radio resources are preempted or not, forexample, based on the preemption indicator comprised in the first DCI.The one or more wireless devices may adjust a transmission power onfirst PUSCH resource(s), for example, based on an indication of the atleast one power reduction and the preemption indicator.

The first PUSCH resource(s) may comprise at least one of the multipleuplink radio resources, which may be preempted by the first DCI. The oneor more wireless devices may determine a power reduction, for example,based on the indication of the at least one power reduction. The one ormore wireless devices may determine an adjusted transmission power, forexample, based on the power reduction and a normal transmission power(e.g., the current transmission power before the transmission poweradjustment). The one or more wireless devices may continue transmittingthe first uplink data with the adjusted transmission power (e.g., in asecond slot or in a second symbol duration). The one or more wirelessdevices may stop (or suspend) transmitting the first uplink data, forexample, if the indication of the at least one power reduction indicatesthe stopping (or suspending) of the uplink transmission (e.g., in thesecond slot or in the second symbol duration).

The first PUSCH resource(s) may comprise at least one of the multipleuplink radio resources, which is not preempted by the first DCI. The oneor more wireless devices may continue the first uplink data transmissionwithout stopping or suspending the transmission (e.g., the indication ofthe at least one power reduction may not be used for non-preemptedresources).

FIG. 25 shows an example of DCI signaling for multiplexing uplink datawith different transmission durations. FIG. 26 shows an example of apower control for multiplexing uplink data with different transmissiondurations. A base station may indicate a first power reduction of atransmission on a first uplink radio resource, which may be differentfrom a second power reduction of a transmission on a second radio uplinkresource.

A base station 2610 (e.g., the base station 2010) may send, to a groupof wireless devices 2620-1, 2620-2, . . . , and 2620-K (e.g., thewireless devices 2021 and 2022), the first DCI 2060 (e.g., in slot 1).The first DCI 2060 (e.g., group DCI 2560) may comprise one or more TPCcommands and/or a preemption indicator. A first one of the one or moreTPC commands may be associated with a first one of multiple uplink radioresources, and the first one of multiple uplink radio resources may bepreempted. There may be no TPC command associated with a second one ofthe multiple uplink radio resources, for example, if the second one ofthe multiple uplink radio resources is not preempted.

A wireless device may determine whether the multiple uplink radioresources are preempted or not, for example, based on the preemptionindicator comprised in the first DCI 2060. The wireless device mayadjust a transmission power on a first PUSCH, for example, based on theindication of the at least one power reduction and the preemptionindicator.

The wireless device may determine a power reduction based on a TPCcommand associated with the at least one uplink radio resource, forexample, if the first PUSCH resource comprises at least one of themultiple uplink radio resources, which may be preempted based on anindication by the first DCI 2060. The wireless device may determine anadjusted transmission power, for example, based on the power reductionand a current transmission power. The wireless device may continuetransmitting the first uplink data with the adjusted transmission powerin a second slot (e.g., slot m) or in a second symbol duration.

The wireless device may continue transmitting the first uplink datawithout applying a power reduction (e.g., indicated by any TPC commandin the first DCI), for example, if the first PUSCH resource comprises atleast one of the multiple uplink radio resources, which may not bepreempted based on an indication in the first DCI.

FIG. 27 shows an example of signaling in which a preemption indicationmay be jointly indicated with a power control command. The first DCI2060 (e.g., group DCI 2760) may comprise a power/preemption indicator.The power/preemption indicator may comprise multiple power/preemptionfields. The power/preemption indicator may comprise any number of bits(e.g., 14 bits or any other number). Each power/preemption field may beone bit. Each power/preemption field may be associated with one of themultiple uplink radio resources. An uplink radio resource associatedwith the power/preemption field may not be preempted (or reserved), forexample, if a power/preemption field of the power/preemption indicatoris set to a first value (e.g., zero). An uplink radio resourceassociated with the power/preemption field may be preempted (orreserved), and/or a transmission power on an uplink transmission on theuplink radio resource may be reduced with a first value, for example, ifa power/preemption field of the power/preemption indicator is set to asecond value (e.g., one). The first value may be predefined (e.g., 3 dB,or 6 dB, 9 dB). The first value may be indicated in an RRC message.

The power/preemption indicator may comprise, for example, 28 bits (orany other number of bits). Each power/preemption field may be two bits.Each power/preemption field may be associated with one of the multipleuplink radio resources. An uplink radio resource associated with thepower/preemption field may not be preempted (or reserved), for example,if a power/preemption field of the power/preemption indicator is set toa first value (e.g., “00”). An uplink radio resource associated with thepower/preemption field may be preempted (or reserved), and atransmission power on an uplink transmission on the uplink radioresource may be reduced with a first value (e.g., 3 dB), for example, ifa power/preemption field of the power/preemption indicator is set to asecond value (e.g., “01”). An uplink radio resource associated with thepower/preemption field may be preempted (or reserved), and atransmission power on an uplink transmission on the uplink radioresource may be reduced with a second value (e.g., 6 dB), for example,if a power/preemption field of the power/preemption indicator is set toa third value (e.g., “10”). An uplink radio resource associated with thepower/preemption field may be preempted (or reserved), and atransmission power on an uplink transmission on the uplink radioresource may be reduced with a third value (e.g., 9 dB), for example, ifa power/preemption field of the power/preemption indicator is set to afourth value (e.g., “11”). The power/preemption indicator may have Mtimes N bits. Each power/preemption field may be M bits. Eachpower/preemption field may be associated with one of N multiple uplinkradio resources. Each power/preemption field may indicate apower/preemption indication on an uplink radio resource associated withthe each power/preemption field.

First DCI may be sent (e.g., transmitted) using a DCI format that is thesame as second DCI (e.g., DCI format 2_0, 2_1, 2_2, or 2_3), forexample, if the first DCI comprises one power/preemption indicator. Thefirst DCI may be addressed to wireless device(s) associated with a groupcommon RNTI different from the second DCI (e.g., DCI format 2_0 withSFI-RNTI, or DCI format 2_1 with INT-RNTI, DCI 2-2 with TPC-PUCCH-RNTIor TPC-PUSCH-RNTI, DCI 2_3 with TPC-SRS-RNTI).

The first DCI may comprise multiple TPC commands and/or multiplepreemption indicators, for example, if the first DCI is configured withmultiple cells. The first DCI may comprise multiple power/preemptionindicators, for example, if the first DCI is configured with multiplecells.

FIG. 28 shows an example of signaling in which TPC commands may beassociated with one of the multiple preemption indicators. Group DCI2860 may comprise a plurality of TPC fields and a plurality ofpreemption indicators. A preemption indicator may be associated with oneof the multiple cells (e.g., Cell 1, Cell 2, . . . , and Cell N). Theassociation between a preemption indicator and a cell may be indicatedin an RRC message. A first TPC command may be implicitly or explicitlyassociated with a first preemption indicator. A second TPC command maybe implicitly or explicitly associated with a second preemptionindicator. An Nth TPC command may be implicitly or explicitly associatedwith an Nth preemption indicator.

A wireless device may receive, from a base station, at least one uplinkpacket on a PUSCH in at least one uplink slot. The wireless device maymonitor a PDCCH on at least a first part of at least one downlink slot,for example, for detecting DCI. The DCI may comprise at least one of:one power control command and/or one parameter indicating whether asecond part of the at least one uplink slot is reserved (or preempted).The wireless device may determine a transmission power of the at leastone uplink packet in the second part of the at least one uplink slot,for example, based on the one power control command. The wireless devicemay determine the transmission power of the at least one uplink packetin the second part of the at least one uplink slot, for example, basedon or in response to detecting the DCI and the at least one parameterindicating the one second part of the at least one uplink slot isreserved (or preempted). The wireless device may send (e.g., transmit)the at least one uplink packet in the at least second part of the atleast one uplink slot using the determined transmission power.

FIG. 29 shows an example method for a power control for multiplexinguplink data with different transmission durations. One or more steps ofFIG. 29 may be performed by a base station. At step 2901, the basestation may establish an RRC connection with a first wireless device andmay send, to the first wireless device, one or more messages (e.g., anRRC message) and/or one or more DCIs. The one or more messages maycomprise configuration parameters for configuring a downlinktransmission (e.g., a PDCCH transmission, a PDSCH transmission, etc.).The one or more messages and/or the one or more DCIs may compriseconfiguration parameters for configuring an uplink transmission (e.g., aPUCCH transmission, a PUSCH transmission, etc.). The first wirelessdevice may receive configuration parameters comprising a first TPCcommand indicating a first transmission power adjustment of transmittinguplink data (e.g., PUSCH). At step 2902, the base station may send anuplink grant to the first wireless device. The base station may scheduleand assign a plurality of uplink radio resources (e.g., the first PUSCHresource 2031, the second PUSCH resource 2032, etc.) for the firstwireless device for an uplink data transmission. The first wirelessdevice may begin to send a first portion of uplink data with atransmission power, for example, based on the uplink grant and the firstTPC command. The base station may assign, to a second wireless device,at least one resource of the plurality of uplink radio resources, andmay preempt the at least one resource. At step 2903, the base stationmay determine whether to reduce power or to stop an uplink transmission,of the first wireless device, on the preempted resource(s). The basestation may determine, based on a capability of the base station and/orthe first wireless device, whether to reduce power or to stop an uplinktransmission on the preempted resource(s).

At step 2094, the base station may determine a first TPC value for oneor more preempted resources, for example, if the base station determinesto reduce a transmission power of the first wireless device for the oneor more preempted resources. At step 2905, the base station may send, tothe first wireless device, DCI comprising a TPC field and a preemptionindicator field. The TPC field may indicate the first TPC valueindicating the reduction of the transmission power of the first wirelessdevice. At step 2906, the base station may receive, via the one or morepreempted resources, uplink data from multiple wireless devices. Themultiple wireless devices may comprise the first wireless device and thesecond wireless device. For the uplink transmissions via the one or morepreempted resources, the second wireless device may set a transmissionpower greater than a transmission power of the first wireless device(e.g., based on configuration parameters for the second wirelessdevice). The first wireless device may reduce a transmission power whilethe first wireless device sends a second portion of the uplink data viathe one or more preempted resources. The first wireless device mayincrease (e.g., restore or recover) the transmission power, for example,if the first wireless device sends a third portion of the uplink datavia one or more non-preempted resources. The first wireless device(e.g., the wireless device 2022) may send, via a first non-preemptedportion of the second PUSCH resource 2032, the first portion of theuplink data. The first wireless device may send, via the one or morepreempted resources (e.g., preempted resources 2033 in the multipleuplink radio resources 2071), the second portion of the uplink data witha reduced power. The first wireless device may send, via a secondnon-preempted portion of the second PUSCH resource 2032, the thirdportion of the uplink data with an increased (e.g., restored) power. Thefirst non-preempted portion of the second PUSCH resource 2032 mayprecede in time the one or more preempted resources. The one or morepreempted resources may precede in time the second non-preempted portionof the second PUSCH resource 2032.

At step 2907, the base station may determine a second TPC value for oneor more preempted resources, for example, if the base station determinesto stop an uplink transmission of the first wireless device for the oneor more preempted resources. The second TPC value may be set to apredefined value. At step 2908, the base station may send, to the firstwireless device, DCI comprising a TPC field and a preemption indicatorfield. The TPC field may indicate the second TPC value indicatingstopping of an uplink transmission of the first wireless device. At step2909, the base station may receive, via the one or more preemptedresources, uplink data from the second wireless device but not from thefirst wireless device. The first wireless device may stop an uplinktransmission while the second wireless device sends uplink data via theone or more preempted resources. The first wireless device may resume anuplink transmission by transmitting a second portion of the uplink data,for example, if the first wireless device sends the second portion ofthe uplink data via one or more non-preempted resources. The firstwireless device (e.g., the wireless device 2022) may send, via a firstnon-preempted portion of the second PUSCH resource 2032, the firstportion of the uplink data. The first wireless device may stop an uplinktransmission on the one or more preempted resources (e.g., preemptedresources 2033 in the multiple uplink radio resources 2071). The firstwireless device may send, via a second non-preempted portion of thesecond PUSCH resource 2032, the second portion of the uplink data. Thefirst non-preempted portion of the second PUSCH resource 2032 mayprecede in time the one or more preempted resources. The one or morepreempted resources may precede in time the second non-preempted portionof the second PUSCH resource 2032.

A single DCI may comprise a first TPC field indicating reducing of atransmission power for a first preempted resource and comprise a secondTPC field indicating stopping of an uplink transmission for a secondpreempted resource. The first TPC field may be associated with a firstUL preemption indicator that indicates the first preempted resource. Thesecond TPC field may be associated with a second UL preemption indicatorthat indicates the second preempted resource. The single DCI may have aformat of the DCI 2560 shown in FIG. 26 , a format of the DCI 2760 shownin FIG. 27 , or other formats.

FIG. 30 shows an example method for a power control for multiplexinguplink data with different transmission durations. One or more steps ofFIG. 30 may be performed by a first wireless device. At step 3001, thefirst wireless device may establish an RRC connection with a basestation and may receive, from the base station, one or more messages(e.g., an RRC message) and/or one or more DCIs. The one or more messagesmay comprise configuration parameters for configuring a downlinktransmission (e.g., a PDCCH transmission, a PDSCH transmission, etc.).The one or more messages and/or the one or more DCIs may compriseconfiguration parameters for configuring an uplink transmission (e.g., aPUCCH transmission, a PUSCH transmission, etc.). The first wirelessdevice may receive configuration parameters comprising a first TPCcommand indicating a first transmission power adjustment of transmittinguplink data (e.g., PUSCH). At step 3002, the first wireless device mayreceive an uplink grant from the base station. The base station mayschedule and assign a plurality of uplink radio resources (e.g., thefirst PUSCH resource 2031, the second PUSCH resource 2032, etc.) for thefirst wireless device for an uplink data transmission. At step 3002, thefirst wireless device may begin to send a first portion of uplink data,for example, based on the uplink grant and the first TPC command. Thebase station may determine to assign, to a second wireless device, atleast one resource of the plurality of uplink radio resources, and maydetermine to preempt the at least one resource. At step 3003, the firstwireless device may receive DCI comprising a second TPC field and apreemption indicator field. At step 3004, the first wireless device maydetermine, based on a value of the second TPC field, whether to reducepower or to stop an uplink transmission on one or more preemptedresources. The preemption indicator field may be associated with thesecond TPC field and may indicate the one or more preempted resources.

At step 3005, the first wireless device may determine that the secondTPC field indicates a first TPC value for one or more preemptedresources. The first TPC value may indicate the reduction of thetransmission power of the first wireless device. At step 3006, the firstwireless device may send, via the one or more preempted resources, asecond portion of the uplink data. The first wireless device may reducea transmission power while the first wireless device sends the secondportion of the uplink data via the one or more preempted resources. Thefirst wireless device may increase (e.g., restore or recover) thetransmission power, for example, if the first wireless device sends athird portion of the uplink data via one or more non-preemptedresources.

At step 3007, the first wireless device may determine that the secondTPC field indicates a second TPC value for one or more preemptedresources (e.g., the second TPC value may be set to a predefined value).The second TPC value may indicate the stopping of the uplinktransmission of the first wireless device. At step 3008, the firstwireless device may stop an uplink transmission via the one or morepreempted resources. The first wireless device may stop the uplinktransmission while a second wireless device sends uplink data via theone or more preempted resources. The first wireless device may resume anuplink transmission by transmitting a second portion of the uplink data,for example, if the first wireless device sends the second portion ofthe uplink data via one or more non-preempted resources.

A base station may send, to a wireless device, one or more messagescomprising configuration parameters indicating uplink radio resourcesfor the wireless device. The base station may send, to the wirelessdevice, a first DCI. The first DCI may comprise a first power controlcommand associated with one or more preempted resources and comprise anuplink preemption indicator indicating that at least one resource of theuplink radio resources is preempted. The wireless device may determine,based on the first power control command and the uplink preemptionindicator, an adjusted transmission power associated with transmission,via the at least one resource, of a first portion of uplink data (e.g.,one or more uplink data packets). The wireless device may transmit,based on the adjusted transmission power and via the at least oneresource, the first portion of the uplink data. The wireless device maydetermine, based on the uplink preemption indicator and based on a valueof the first power control command, whether to reduce a transmissionpower to the adjusted transmission power or to stop transmission of thefirst portion of the uplink data. The wireless device may transmit thefirst portion of the uplink data further based on the determining. Thewireless device may monitor a first downlink control channel for thefirst DCI. The uplink preemption indicator may comprise a value of onebit or multiple bits. The configuration parameters may indicate at leastsecond radio resources. The uplink radio resources may comprise a firstnumber of frequency resources and a second number of time resources. Thewireless device may determine, based on the first power control commandand the uplink preemption indicator, a power value for reducing thetransmission power. The wireless device may receive a second DCIindicating a second transmission power value. The wireless device maysubtract, from a second transmission power value, the power value todetermine the reduced transmission power. The second transmission powervalue may be comprised in second DCI. The wireless device may receivethe second DCI during a first time interval that is a number of timeinterval before the wireless device receives the first DCI. The wirelessdevice may determine, based on the second transmission power value, asecond transmission power associated with transmission, via a secondresource of the uplink radio resources, of a second portion of theuplink data. The second resource may not be preempted by the uplinkpreemption indicator. The wireless device may adjust the transmissionpower by determining, based on the first power control command, a powerreduction value and determining, based on the second transmission powervalue and the power reduction value, the adjusted transmission power.The uplink preemption indicator may comprise a plurality of preemptionindicator values each associated with a different uplink radio resourceof the uplink radio resources. The wireless device may determine thatone or more values of the plurality of preemption indicator values isset to a first value indicating preemption of a corresponding radioresource. The wireless device may identify, based on a location of theone or more values in the first DCI, one or more preempted uplinkresources of the uplink radio resources. The first DCI may comprise atleast one second preemption indicator. The at least one secondpreemption indicator may be associated with at least one second uplinkradio resource. The at least one second preemption indicator may beassociated with the at least one second uplink radio resource, forexample, based on a location of the at least one second preemptionindicator in the first DCI. The wireless device may determine, based ona second uplink preemption indicator of the first DCI, one or moresecond uplink radio resources are not preempted. The wireless device maydetermine, based on a second power control command, a secondtransmission power associated with transmission, via the one or moresecond uplink radio resources, of a second portion of the uplink data.The wireless device may transmit, via the one or more second uplinkradio resources and based on the second transmission power, the secondportion of the uplink data. The wireless device may receive, during afirst time interval, a second DCI comprising the second power controlcommand.

A base station may send, to a wireless device, one or more messagescomprising configuration parameters. The base station may send, to thewireless device, first DCI indicating a first power control command anda plurality of uplink radio resources for the wireless device. The basestation may send, to the wireless device, second DCI comprising a secondpower control command associated with one or more preempted resourcesand an uplink preemption indicator indicating that a first uplink radioresource of the plurality of uplink radio resources is not preempted.The wireless device may determine, based on the uplink preemptionindicator indicating that the first uplink radio resource is notpreempted, to transmit a portion of uplink data based on the first powercontrol command. The wireless device may select the first power controlcommand, for example, based on the uplink preemption indicator. Thewireless device may transmit, via the first uplink radio resource andbased on the first power control command, the portion of the uplinkdata. The uplink preemption indicator may indicate that a second uplinkradio resource of the plurality of uplink radio resources is preempted.The wireless device may determine, based on the uplink preemptionindicator and based on a value of the second power control command,whether to reduce a transmission power associated with transmission, viathe second uplink radio resource, of a second portion of the uplink dataor to stop transmission of the second portion of the uplink data. Thewireless device may transmit, via the second uplink radio resource andbased on a reduced transmission power, the second portion, or stoptransmission, via the second uplink radio resource, of the secondportion, for example, based on the determining. The wireless device maydetermine, based on the second power control command and the uplinkpreemption indicator, an adjusted transmission power associated withtransmission, via the second uplink radio resource, of a second portionof the uplink data. The wireless device may transmit, based on theadjusted transmission power and via the second uplink radio resource,the second portion of the uplink data. A wireless device may transmit afirst portion of uplink data. A bases station may send, to the wirelessdevice, a DCI comprising one or more parameters indicating a powercontrol associated with one or more resources. The wireless device maydetermine, based on the one or more parameters of the DCI, whether toreduce a transmission power associated with transmission, via apreempted resource, of a second portion of the uplink data or to stoptransmission of the second portion of the uplink data. The wirelessdevice may transmit, via the preempted resource and based on a reducedtransmission power, the second portion, or stop transmission, via thepreempted resource, of the second portion, for example, based on thedetermining. The one or more parameters of the DCI may comprise a powercontrol command and an uplink preemption indicator. The wireless devicemay determine, based on the power control command and the uplinkpreemption indicator, the reduced transmission power. The wirelessdevice may determine, based on the one or more parameters of the DCI, anon-preempted resource. The wireless device may transmit, via thenon-preempted resource and based on a second power control command, athird portion of the uplink data. A predefined value of the one or moreparameters indicates the stopping. The one or more parameters maycomprise a first transmission power control field associated with afirst cell and a second transmission power control field associated witha second cell. The one or more parameters may comprise a first uplinkpreemption indicator field associated with the first cell and associatedwith the first transmission power control field and a second uplinkpreemption indicator field associated with the second cell andassociated with the second transmission power control field.

FIG. 31 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 3100 may include one ormore processors 3101, which may execute instructions stored in therandom access memory (RAM) 3103, the removable media 3104 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive3105. The computing device 3100 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 3101 andany process that requests access to any hardware and/or softwarecomponents of the computing device 3100 (e.g., ROM 3102, RAM 3103, theremovable media 3104, the hard drive 3105, the device controller 3107, anetwork interface 3109, a GPS 3111, a Bluetooth interface 3112, a WiFiinterface 3113, etc.). The computing device 3100 may include one or moreoutput devices, such as the display 3106 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 3107, such as a video processor. There mayalso be one or more user input devices 3108, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device3100 may also include one or more network interfaces, such as a networkinterface 3109, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 3109 may provide aninterface for the computing device 3100 to communicate with a network3110 (e.g., a RAN, or any other network). The network interface 3109 mayinclude a modem (e.g., a cable modem), and the external network 3110 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 3100 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 3111, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 3100.

The example in FIG. 31 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 3100 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 3101, ROM storage 3102, display 3106, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 31 .Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, information comprising: a plurality of power control commands;and a set of uplink preemption indicators that is associated with apower control command of the plurality of the power control commands andthat indicates which one or more uplink resources, of a set of uplinkresources, are preempted; and dropping, based on the power controlcommand of the plurality of the power control commands, a scheduleduplink transmission via at least one preempted uplink resource of theset of uplink resources indicated by the set of uplink preemptionindicators.
 2. The method of claim 1, wherein the information furthercomprises: a second set of uplink preemption indicators that isassociated with a second power control command of the plurality of thepower control commands and that indicates which one or more uplinkresources, of a second set of uplink resources, are preempted; andwherein the method further comprises transmitting, based on the secondpower control command of the plurality of the power control commands,uplink data via at least one preempted uplink resource of the second setof uplink resources indicated by the second set of uplink preemptionindicators.
 3. The method of claim 1, wherein the power control command,of the plurality of power control commands, is associated with droppingof scheduled uplink transmission associated with the at least onepreempted uplink resource of the set of uplink resources indicated bythe set of uplink preemption indicators, and wherein a second powercontrol command, of the plurality of power control commands, isassociated with an adjusted transmission power for transmission ofuplink data.
 4. The method of claim 1, further comprising: determiningthe set of uplink resources from a plurality of sets of uplinkresources, wherein each set of the plurality of sets of uplink resourcesis associated with one of the plurality of power control commands. 5.The method of claim 1, wherein the receiving the information comprisesreceiving the information in at least one of: downlink controlinformation (DCI); a radio resource control (RRC) message; or a mediumaccess control (MAC) control element (CE).
 6. The method of claim 1,wherein the set of uplink preemption indicators comprises a bit, foreach uplink resource of the set of uplink resources, that indicateswhether that uplink resource is preempted.
 7. The method of claim 1,further comprising: receiving one or more configuration parameterscomprising a second power control command indicating a power adjustmentvalue; and transmitting, based on the power adjustment value, uplinkdata via one or more uplink resources that are not preempted.
 8. Themethod of claim 1, wherein the power control command, of the pluralityof power control commands, is associated with a first cell, and whereina second power control command, of the plurality of power controlcommands, is associated with a second cell that is different from thefirst cell.
 9. The method of claim 1, further comprising: receiving oneor more configuration parameters comprising a power control commandassociated with a power adjustment value; and determining, based on thepower adjustment value and a value of a second power control command ofthe plurality of power control commands, an uplink power fortransmission of uplink data via at least one preempted uplink resourceof a second set of uplink resources.
 10. A method comprising: receiving,by a wireless device, first information indicating: a first powercontrol command; and a plurality of uplink radio resources for thewireless device; receiving second information comprising: a second powercontrol command associated with one or more preempted resources; and anuplink preemption indicator, associated with the one or more preemptedresources, indicating a first uplink radio resource of the plurality ofuplink radio resources that is not preempted; and transmitting, based onthe uplink preemption indicator indicating the first uplink radioresource that is not preempted and using a transmission power associatedwith the first power control command, a portion of uplink data via thefirst uplink radio resource.
 11. The method of claim 10, wherein theuplink preemption indicator indicates a second uplink radio resource ofthe plurality of uplink radio resources that is preempted.
 12. Themethod of claim 11, further comprising: dropping, based on the uplinkpreemption indicator and based on the second power control command, ascheduled transmission of a second portion of the uplink data.
 13. Themethod of claim 11, further comprising: determining, based on the secondpower control command and the uplink preemption indicator, an adjustedtransmission power associated with transmission, via the second uplinkradio resource, of a second portion of the uplink data; andtransmitting, using the adjusted transmission power and via the seconduplink radio resource, the second portion of the uplink data.
 14. Themethod of claim 10, wherein the second power control command comprises:a first transmission power control field associated with a first cell;and a second transmission power control field associated with a secondcell.
 15. The method of claim 10, wherein the receiving the secondinformation comprises receiving the second information in at least oneof: downlink control information (DCI); a radio resource control (RRC)message; or a medium access control (MAC) control element (CE).
 16. Awireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive information comprising: a plurality ofpower control commands; and a set of uplink preemption indicators thatis associated with a power control command of the plurality of the powercontrol commands and that indicates which one or more uplink resources,of a set of uplink resources, are preempted; and drop, based on thepower control command of the plurality of the power control commands, ascheduled uplink transmission via at least one preempted uplink resourceof the set of uplink resources indicated by the set of uplink preemptionindicators.
 17. The wireless device of claim 16, wherein the informationfurther comprises: a second set of uplink preemption indicators that isassociated with a second power control command of the plurality of thepower control commands and that indicates which one or more uplinkresources, of a second set of uplink resources, are preempted; andwherein the instructions, when executed by the one or more processors,cause the wireless device to transmit, based on the second power controlcommand of the plurality of the power control commands, uplink data viaat least one preempted uplink resource of the second set of uplinkresources indicated by the second set of uplink preemption indicators.18. The wireless device of claim 16, wherein the power control command,of the plurality of power control commands, is associated with droppingof scheduled uplink transmission associated with the at least onepreempted uplink resource of the set of uplink resources indicated bythe set of uplink preemption indicators, and wherein a second powercontrol command, of the plurality of power control commands, isassociated with an adjusted transmission power for transmission ofuplink data.
 19. The wireless device of claim 16, wherein theinstructions, when executed by the one or more processors, cause thewireless device to: determine the set of uplink resources from aplurality of sets of uplink resources, and wherein each set of theplurality of sets of uplink resources is associated with one of theplurality of power control commands.
 20. The wireless device of claim16, wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to receive the information byreceiving the information in at least one of: downlink controlinformation (DCI); a radio resource control (RRC) message; or a mediumaccess control (MAC) control element (CE).
 21. The wireless device ofclaim 16, wherein the set of uplink preemption indicators comprises abit, for each uplink resource of the set of uplink resources, thatindicates whether that uplink resource is preempted.
 22. The wirelessdevice of claim 16, wherein the instructions, when executed by the oneor more processors, cause the wireless device to: receive one or moreconfiguration parameters comprising a second power control commandindicating a power adjustment value; and transmit, based on the poweradjustment value, uplink data via one or more uplink resources that arenot preempted.
 23. The wireless device of claim 16, wherein the powercontrol command, of the plurality of power control commands, isassociated with a first cell, and wherein a second power controlcommand, of the plurality of power control commands, is associated witha second cell that is different from the first cell.
 24. The wirelessdevice of claim 16, wherein the instructions, when executed by the oneor more processors, cause the wireless device to: receive one or moreconfiguration parameters comprising a power control command associatedwith a power adjustment value; and determine, based on the poweradjustment value and a value of a second power control command of theplurality of power control commands, an uplink power for transmission ofuplink data via at least one preempted uplink resource of a second setof uplink resources.
 25. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive firstinformation indicating: a first power control command; and a pluralityof uplink radio resources for the wireless device; receive secondinformation comprising: a second power control command associated withone or more preempted resources; and an uplink preemption indicator,associated with the one or more preempted resources, indicating a firstuplink radio resource of the plurality of uplink radio resources that isnot preempted; and transmit, based on the uplink preemption indicatorindicating the first uplink radio resource that is not preempted andusing a transmission power associated with the first power controlcommand, a portion of uplink data via the first uplink radio resource.26. The wireless device of claim 25, wherein the uplink preemptionindicator indicates a second uplink radio resource of the plurality ofuplink radio resources that is preempted.
 27. The wireless device ofclaim 26, wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to: drop, based on the uplinkpreemption indicator and based on the second power control command, ascheduled transmission of a second portion of the uplink data.
 28. Thewireless device of claim 26, wherein the instructions, when executed bythe one or more processors, cause the wireless device to: determine,based on the second power control command and the uplink preemptionindicator, an adjusted transmission power associated with transmission,via the second uplink radio resource, of a second portion of the uplinkdata; and transmit, using the adjusted transmission power and via thesecond uplink radio resource, the second portion of the uplink data. 29.The wireless device of claim 25, wherein the second power controlcommand comprises: a first transmission power control field associatedwith a first cell; and a second transmission power control fieldassociated with a second cell.
 30. The wireless device of claim 25,wherein the instructions, when executed by the one or more processors,cause the wireless device to receive the second information by receivingthe second information in at least one of: downlink control information(DCI); a radio resource control (RRC) message; or a medium accesscontrol (MAC) control element (CE).